-
Notifications
You must be signed in to change notification settings - Fork 4
Add extraction for installshield executables. #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add extraction for installshield executables. #27
Conversation
SabreTools.Serialization/Models/InstallShieldExecutable/ExtractableFile.cs
Outdated
Show resolved
Hide resolved
SabreTools.Serialization/Models/InstallShieldExecutable/ExtractableFile.cs
Show resolved
Hide resolved
|
|
||
| namespace SabreTools.Serialization.Readers | ||
| { | ||
| public class InstallShieldExecutableFile : BaseBinaryReader<ExtractableFile> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Future note: This will likely be expanded to cover an entire overlay section and not a singular entry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will I need to do that? I'd be fine with doing it if I understood how it would be expanded to cover that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not in this PR
Handles extraction for installshield executables. I know from experience that this probably won't work with earlier installshield executables that have MSIs inside, and potentially some other kind, but those also might be a different format anyways. Either way, the format is pretty simple and the only potential issues I'm worried about is whether something succeeds in getting the start of its overlay parsed like an installshield exe file entry.